|
When you are
using Windows NT or Win2k you can run FST as a service. In order to install FST as
a service , run "SRVINSTW.EXE" from your "CT-Tools\FileScan
Tool" directory. SRVINSTW is a resource-kit tool
which can run any program as a service.
FST is specifically written to support commands (start/stop/pause...)
from the Service Control Manager. When you install FST as
a service be sure to select "Service is its own
process" and check "Allow service to interact
with desktop". Furthermore it's important NT/2000
doesn't try to start FST to soon. In order to make sure
FST starts at the right time, you must manually add a key
to the registry (I suggest you use REGEDT32);
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FileScan
Tool
The last part "FileScan Tool" is the name you
gave the service when you installed it with SRVINSTW. Add
the following value;
Value Name
: DependOnService
Data Type : REG_MULTI_SZ
Data : LanmanWorkstation
When you use FST as a service be sure to configure the
"AutoStart Settings" of FST as "Enable/NT
Service" and to only start and stop FST from the
Services control-panel!
To help you install FST as a service I have included a
registry-file which will add the necessary keys to your
registry. This way you don't have to use SRVINSTW to
install FST as a service. The registry-file is called
"FST_Service.reg" and is located in
the installation directory (double-click to execute). The
registry-file assumes you have a default installation of
FST;
Installed in "c:\program files\ct-tools\filescan
tool"
If you have installed FST in a different directory you
can still use the registry-file, but will have to use
REGEDT32 to change the keys/values after you run the
registry-file. After running the registry-file and
optionally changing some registry-values, reboot your
computer for the changes to take effect.
The "DependOnService" value will automatically
be added and the service-name will be "FileScan Tool".
NOTE:
When you run FST as a service and you try to copy files
over the network through shares, this will cause a
problem. The reason is that NT by default runs services
with "LocalSystem" privilege. "LocalSystem"
is a hidden built-in account which you cannot see or
change. This account however only has local privileges
and no network privileges.
To circumvent this you can configure the "FileScan
Tool" service to run under a different account which
does have network privileges. Use the "Control Panel\Services\FileScan
Tool\Startup" to configure this. When you do this,
you will see that when you configure the service with
different privileges, you cannot configure it to "Allow
service to interact with desktop". This is not
really a problem, but will prevent FST to put itsself in
the SystemTray, so you cannot "see" FST is
running or easily access the setup. If you want to check
FST is running, you can check the logfile or use the
Taskmanager and look for a "fst" process.
If you now want to (re)configure FST, use "Control
Panel\Services" to stop the service. Start FST from
your Start-Menu (it will run from the SysTray but won't
be active). Now you can right-click the SysTray icon to
enter the setup, make and save your changes and quit FST.
Restart FST from "Control Panel\Services".
|
|